Skip to content

Conversation

@Shekharrajak
Copy link

@Shekharrajak Shekharrajak commented Dec 26, 2025

Ref #393

  • doc-needed
  • doc-not-needed

@github-actions github-actions bot added priority/major Default priority of the PR or issue. fixVersion/0.2.0 The feature or bug should be implemented/fixed in the 0.2.0 version. doc-label-missing The Bot applies this label either because none or multiple labels were provided. labels Dec 26, 2025
@github-actions
Copy link

@Shekharrajak Please add the following content to your PR description and select a checkbox:

- [ ] `doc-needed` 
- [ ] `doc-not-needed` <!-- Your PR changes do not impact docs -->

@github-actions github-actions bot added doc-not-needed Your PR changes do not impact docs and removed doc-label-missing The Bot applies this label either because none or multiple labels were provided. labels Dec 26, 2025
@wenjin272
Copy link
Collaborator

wenjin272 commented Dec 29, 2025

Hi, @Shekharrajak, thanks for your contribution.

I think this document is very detailed and specific, thank you for your hard work.

However, we might not want to dedicate such a long section to covering all dependency details. Instead, we could briefly introduce, in the section like "Installation," which artifacts users should depend on when developing Agent applications based on flink-agents (api + integration). Also, what additional dependencies are needed if one wants to run it in an IDE. (runtime + flink artifacts)

WDYT?

@Shekharrajak
Copy link
Author

Thanks @wenjin272 for the review. Check the new commit : 891f52f


**Required for developing Agent applications:**
- `flink-agents-api` - Core API interfaces and classes
- Integration modules - Add the specific integrations you need (e.g., `flink-agents-integrations-chat-models-openai`)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In #433, we add constant strings to point a resource implementation, so integration modules is not required for developing. But they are still need for running in IDE

@wenjin272
Copy link
Collaborator

Hi, @xintongsong, could you help review this PR?

Due to our recent changes to the API, one part of the documentation needs to be updated accordingly. However, since @Shekharrajak has not responded recently, we can make this update separately after merging this PR.

@xintongsong xintongsong added doc-included Your PR already contains the necessary documentation updates. and removed doc-not-needed Your PR changes do not impact docs labels Jan 20, 2026
Comment on lines +180 to +185
<!-- Runtime (required for IDE/local execution) -->
<dependency>
<groupId>org.apache.flink</groupId>
<artifactId>flink-agents-runtime</artifactId>
<version>${flink-agents.version}</version>
</dependency>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this also be provided?

Comment on lines +204 to +206
{{< hint info >}}
**Note:** Replace `0.2-SNAPSHOT` with the actual release version when available. For SNAPSHOT versions, you may need to add the Apache snapshot repository to your `pom.xml`.
{{< /hint >}}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we can remove this hint and just use 0.2 w/o the -SNAPSHOT suffix. The version will soon be available in 1-2 weeks.

<scope>provided</scope>
</dependency>
</dependencies>
```
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have a feeling that there are too many dependencies need to be added for execution in an IDE. This not only harms the user experience, but also makes this document hard to maintain as the dependencies need to be added may change in future and this document can easily become inconsistent. I wonder if we can introduce a pom like flink-agents-ide-supports, which includes all dependencies needed for the local execution. Of course this can be a separate issue and should not block this PR.
cc @wenjin272

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

doc-included Your PR already contains the necessary documentation updates. fixVersion/0.2.0 The feature or bug should be implemented/fixed in the 0.2.0 version. priority/major Default priority of the PR or issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants